PHI 1 - Labeled Tuples #4
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cyrus-
requested changes
May 12, 2020
|
|
||
| ### Expression Syntax Errors | ||
|
|
||
| + A label must be followed by a valid expression and comma operator, not another label. For example, `.label1 .label2 e` produces an error. |
cyrus-
requested changes
May 19, 2020
| TODO: partially labeled values, where some of the arguments are in order: `(1, 2, .z 3) <= (.x Num, .y Num, .z Num)`. what about interleaving vs. requiring all the explicit labels at the end ala Python? | ||
| TODO: what are the type synthesis and type analysis rules for the labeled tuple expressions --> | ||
| ### Punning | ||
| Some languages, such as Reason, have record punning. This is where a record's labels can be implied when it is declared using variables. For example, `{x, y, z} => {x: x, y: y, z: z}` is true. Similar punning fuctionality could be implemented in Hazel. For example, if this punning was implemented `(x, y, z) => (x: x, y: y, z: z)` would hold true. However, this creates a question of if every tuple created with variables should be a labeled tuple. Given this additional complexity and added development costs, I believe that labeled tuple punning should be considered out of scope for labeled tuples. |
There was a problem hiding this comment.
give the ambiguous example: (y, x, z) -- is this punned or ordered?
1-labeled-tuples/1-labeled-tuples.md
Outdated
| `e.label` will be the new expression form. `e.label` expects `e` to synthesize to a labeled tuple type and `label` to match one of the labels within `e`. | ||
|
|
||
| `e.label` will return the value that has the label `label`. | ||
| #### Backspace |
There was a problem hiding this comment.
separate section on Action Semantics
1-labeled-tuples/1-labeled-tuples.md
Outdated
|  | ||
|
|
||
| #### Analysis | ||
|  |
There was a problem hiding this comment.
don't want to allow a type to be treated as a 1-tuple implicitly, so don't need this rule.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.